Application driven hardware cache management

ABSTRACT

A processor includes a processing core to generate a memory request for an application data in an application. The processor also includes a virtual page group memory management (VPGMM) unit coupled to the processing core to specify a caching priority (CP) to the application data for the application. The caching priority identifies importance of the application data in a cache.

RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 14/748,971 filed Jun. 24, 2015, which is incorporated byreference herein.

TECHNICAL FIELD

The embodiments of the disclosure relate generally to processingdevices, and, more specifically to application driven hardware cachemanagement.

BACKGROUND

In many central processing units, a software controls over allocationsof shared platform resources such as caches. Cache allocation technology(CAT) enables the software to partition the caches between multipleprocesses and allows cache capacity to be reserved for a process or agroup of processes. CAT enables cache resource allocation andperformance isolation based on priority of an application.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure will be understood more fully from the detaileddescription given below and from the accompanying drawings of variousembodiments of the disclosure. The drawings, however, should not betaken to limit the disclosure to the specific embodiments, but are forexplanation and understanding only.

FIG. 1 illustrates a processing system according an embodiment of thedisclosure.

FIG. 2 illustrates an overview of architecture of a virtual page groupmemory management unit according to an embodiment of the disclosure.

FIG. 3 is an overview of a. software flow to enable caching prioritiesfor application data according to an embodiment of the disclosure.

FIG. 4A is a flow diagram of a method defining a group of pages invirtual address space of an application according to an embodiment ofthe disclosure.

FIG. 4B is a flow diagram of a method specifying caching priorities toapplication data according to an embodiment

FIG. 5A is a block diagram illustrating a micro-architecture for aprocessor in which one embodiment of the disclosure may be used.

FIG. 5B is a block diagram illustrating an in-order pipeline and aregister renaming stage, out-of-order issue/execution pipelineimplemented according to at least one embodiment of the disclosure.

FIG. 6 illustrates a block diagram of the micro-architecture for aprocessor in accordance with one embodiment of the disclosure.

FIG. 7 is a block diagram illustrating a system in which an embodimentof the disclosure may be used.

FIG. 8 is a block diagram of a system in which an embodiment of thedisclosure may operate.

FIG. 9 is a block diagram of a system in which an embodiment of thedisclosure may operate.

FIG. 10 is a block diagram of a System-on-a-Chip (SoC) in accordancewith an embodiment of the present disclosure

FIG. 11 is a block diagram of an embodiment of an SoC design inaccordance with the present disclosure.

FIG. 12 illustrates a block diagram of one embodiment of a computersystem.

DETAILED DESCRIPTION

A computing device may include one or more processing cores in one ormore processors (such as central processing units (CPUs)) for executinginstructions and a memory device (such as random-access memory (RAM))for storing instructions and data associated with executing tasks(including user applications and system applications such as the kernelof an operating system) on the one or more processing cores.Instructions of each application program address the memory usingvirtual addresses (or linear addresses) of a virtual memory that may betranslated into physical addresses of the memory by a memory managementunit (MMU) associated with the one or more processors. The task executedon a processing core may be a memory request to access (read or write)memory referenced by the virtual addresses, which may be translated intothe physical addresses of the memory by the MMU.

Existing memory and cache systems in the CPU treat all memory requestsin an application's address space uniformly, with all normal cacheabledata accessed read into the CPU caches. Such existing systems rely onN-way set associative cache designs for cache allocation and rely ongeneric cache replacement algorithms, such as least recently used (LRU)to determine cache lines to evict. However, these systems are not suitedfor current in-memory server applications as they do not account foractual importance of the application data to an application for cacheallocation and eviction decisions. As such, the applications may notoptimally utilize relatively scarce cache resources.

Embodiments of the disclosure overcome the above problems byimplementing application-driven hardware cache management that specifiescaching priorities (CPs) of application data. In one embodiment, a CP isa value assigned to determine importance of data in the cache. The CPvalue may be modified based on a type of application data in theapplication. In one embodiment, the CP value is modified based onrequirements of the application. The CPs can function as hints to theCPU caching systems. In some embodiments, CPs are used to determinecache line evictions. The cache eviction algorithms may use the CPs inaddition to LRU information in their cache replacement algorithms. Inother embodiments, the CPs are used to determine cache allocation. Inone embodiment, the CPs are used to restrict number of ways in an N-wayset associate cache available for the data.

FIG. 1 illustrates a processing system 100 including a processing device102 coupled to a memory 105 to protect the memory according anembodiment of the disclosure. The processing device 102 (such as acentral processing unit (CPU)) may include a virtual page group memorymanagement (VPGMM) unit 112 connected to memory hardware, such as cachememory 194 having cache units. The cache units may include a hierarchyof cache levels stored on the processor 102 and off of the processor. Afastest Level 1 (L1) cache may be included as memory 104 on theprocessor 102. The cache memory 104 may store data associated withsystem application and user application programs executed by theprocessor 102. Additional lower-level caches (e.g., L2, L3, etc.) may belocated both on and off of the processing device 102.

In one embodiment, the processor 102 may further include one or moreprocessing cores 110. The one or more processing cores are the engineswithin the processor 102 for executing tasks, such as the systemapplications and the user application programs. In one embodiment, thetasks executed on processing cores 110 access a virtual memory throughvirtual addresses (also known as linear addresses). The VPGMM unit 112may map the virtual addresses of the virtual memory to the physicaladdresses of the memory (a.k.a. “off chip memory”) 105. The space ofvirtual addresses may be divided into fixed sized units called pages. Apage of the virtual addresses may be mapped correspondingly intofixed-sized units in the space of the physical addresses of the cachememory 104 called memory frames.

In one embodiment, the VPGMM unit 112 may include one or more virtualaddresses pages or page numbers 118 corresponding to a page table 106having one or more page table entries (PTEs) 116 stored in the memory105. The page table entries are also known as leaf nodes of the pagetable 106. In one embodiment, VPGMM unit 112 may perform the memoryaddress mapping. Each of the PTEs 116 may store one or more memory framenumbers that are identified according to the virtual address pagenumbers 118. In one embodiment, a task executing on the processing cores110 may allocate a block of memory by specifying one or more virtualaddress ranges. A virtual address may include a first portion includingone or more bits (e.g., the high-order twenty bits) indicating thevirtual address page number and a second portion of bits (e.g., thelower-order 12 bits) indicating the byte offset within a memory framecorresponding to the page. The PTE 116 stores mappings between pages ofvirtual addresses to physical addresses. The mappings may be the mappingbetween identifiers of pages (or page numbers) to identifiers of memoryframes (or memory frame numbers). The memory frame numbers determine theregion of the cache memory 104 allocated to a task. In one embodiment,these mappings are part of a page table.

The VPGMM 112 may use the virtual address page number 118 to identify amemory frame number stored in the PTE 116, and combine the identifiedmemory frame number 118 and the offset byte to form a physical address,corresponding to the PTEs 116 stored in the page table 106 in the memory105. The physical address corresponding to the virtual address may bestored in a buffer.

In one embodiment, the VPGMM unit 112 enables applications to assign thepages 118 in its virtual addresses to a virtual page group (VPG). TheVPGMM unit 112 assigns an identification denoted by VPGID to the VPG.The VPGMM unit 112 may add a set of pages in an application's virtualaddress to an existing VPG denoted by the VPGID. The VPGMM unit 112 maydelete a set of pages in the application's virtual address from analready-existing VPG denoted by the VPG ID. The VPGMM unit 112 maydelete the VPG denoted by the VPGID. In one embodiment, the VPGID isstored in the PTE 116. In one embodiment, the VPGID is associated withthe virtual address stored in the PTE 116. As such, the VPGID isassigned to each of the PTEs in the virtual address.

In one embodiment, the VPGMM 112 may include a virtual page groupcaching priority (VPGCP) table 114. In one embodiment, the VPGCP table114 includes a caching priority (CP) specifically assigned to the VPG inthe application's virtual address stored in the PTE 116. As such, theVPGCP table 114 represents the CP corresponding to the VPGID (stored inthe virtual address age 118) of the VPG. In one embodiment, a CP is avalue assigned to determine importance of caching data in the cachememory 104. In one embodiment, the CP is a priority assigned toapplication data of an application. In one embodiment, the CP isassigned based on requirements of the application data. Some ofrequirements of the application may include, but are not limited toapplication's ability to classify application data based on relativeimportance and ability to convey the information to the system softwaremanaging VPGCP table. In one embodiment, the CP is assigned based on atype of the application data. Some examples of types of data mayinclude, but are not limited to, index data and table data in adatabase.

In one embodiment, the VPGMM unit 112 may include logics that enable CPsfor the application data and define the VPG in the application's addressspace to which a specific CP is applied as described in greater detailwith respect to FIG. 2 and FIG. 3 below. In one embodiment, the VPGMMunit 112 enables applications to directly modify CP value assigned to aVPG in the VPGCP table 114. In one embodiment, the modified CP for theapplication is applied for the application data in the cache. In oneembodiment, the modified CP is used to determine cache allocation. Inone embodiment, the modified CP is used to make cache evictiondecisions. In one embodiment, the VPGMM unit assigns a default value of0 (i.e. highest priority) to each of the CPs assigned to the VPG in theVPGCP table 114. In one embodiment, the VPGMM unit modifies the defaultvalue of the CP assigned to the VPG in the VPGCP table 114.

In one embodiment, the VPGMM unit 112 may include an AND logic 122including a first input received from the PTE 116 and a second inputreceived from the VPGCP table 114. The first input is the translation ofthe virtual address to physical address. The second input is the CPassigned to the virtual address of the VPG that the PTE is assigned to.The AND logic 122 may combine the CP received from the VPGCP table 114with the virtual to physical address translation received from the PTE116 to populate the translation look-aside buffers (TLBs) into the cachememory 104. In one embodiment, the TLB functions to address or look updata in the cache memory 104 for faster retrieval.

In one embodiment, in response to a request by a task executing on thecores 110 to access memory frames whose identifiers are stored in thePTE 116, the VPGMM unit 112 may enable to specify CPs in its virtualspace in order to provide importance of caching some application dataover others.

FIG. 2 illustrates an overview of architecture of a VPGMM unit 200according to an embodiment of the disclosure. In one embodiment, theVPGMM unit 200 is same as the VPGMM 112 of FIG. 1. As shown in FIG. 2,the VPGMM unit 200 may include a virtual address page 218 correspondingto the page table (not shown). The virtual address page 218 is same asthe virtual address page 118 of FIG. 1. As discussed above, the PTE 216contains mapping of a page in an application's virtual address (VA)space to an actual physical address (PA). In one embodiment, each page218 in the application's virtual memory may be assigned to a single VPG,which is denoted by a VPGID 220. Each of the VPG is assigned a CP andeach of the pages in the VPG are assigned to the same CP. The CP isstored in a VPGCP table 214. The VPGCP table 214 is same as the VPGCPtable of FIG. 1. As shown, the VPGID 220 indexes the VPGCP table 214that contains the CP assigned to the VPG. In one example, the CP isassigned a value in a number in the range of 0 to Max_CP. In oneembodiment, higher number values in the range imply a lower cachingpriority and a higher preference for eviction from the caches. Inanother embodiment, the lower number values such as 0 in the range implya higher caching priority with a lower preference for eviction from thecaches.

In one embodiment, the CP is specified for a virtual page group (VPG).The CP may be mapped to a virtual address. As such, each of the VPGsdenoted by their corresponding VPGIDs 220 in the VPGCP table 114 isassigned with a CP. In one embodiment, the CP assigned to the VPGID ofthe VPG is updated by changing entries directly in the VPGCP table 214.In one embodiment, by default each of the VPGIDs of the VPGs is assignedwith a value of CP to be 0 (i.e. highest priority). In one embodiment,the value of the CP assigned to the VPGID of the VPG is modified bylowering the value of the CP for the VPG in the VPGCP table 214.

In one embodiment, the VPGMM unit 200 may include an AND logic 222including a first input received from the virtual address page 218, anda second input received from the VPGCP table 214. The first input is thetranslation of the virtual address of the VPG to physical address andthe second input is the CP assigned to the VPG that the virtual addressbelongs to. The output of the AND logic 222 may provide for a TLB fillinto the cache memory.

FIG. 3 illustrates an overview of a flow 300 to enable cachingpriorities for application data. In one embodiment, each of applicationdata 302 and 304 is assigned to a priority CP (x) and CP (y)respectively. In one embodiment, each application data 302 and 304corresponds to a memory pool 306 and 308 respectively. In oneembodiment, each of the memory pools 306 and 308 is a buffer defining arange of memory to allocate the application data 302 and 304respectively. In one embodiment, each memory pool 306 and 308 isassigned to at least one VPG 310 and 312 respectively. In oneembodiment, the application data 302 and 304 from each of the memorypools 306 and 308 is allocated to corresponding VPG 310 and 312. In oneembodiment, based on requirements of the application, each of theapplication data 302 and 304, the corresponding VPG 310 and 312 isassigned a CP. Some of the requirements of the application may include,but are not limited to application's ability to classify applicationdata based on relative importance and ability to convey the informationto the system software managing VPGCP table. In one embodiment, based onthe type of the application data, each of the application data 302 and304, the corresponding VPG 310 and 312 is assigned a CP. Some of thetype of the data may include, but is not limited to, index data andtable data in a database.

In one embodiment, the application data 302 includes index data andtable data. In one embodiment, the memory pool 306 includes two memorypools 306 a and 306 b for the index data and for the table data,respectively, and are assigned to two VPGs 310 a and 310 b,respectively. As such, the index data from the memory pool 306 a isallocated to the VPG 310 a and the table data from the memory pool 306 bis allocated to the VPG 310 b. In one embodiment, the VPG 310 a withindex data is assigned a higher CP. In such embodiment, value of the CPwould be 0 or close to 0. In one embodiment, the VPG 310 b with thetable data is assigned a lower CP. In this embodiment, the CP would begreater than 0.

FIG. 4A is a flow diagram of method 400 of defining a group of pages invirtual address space of an application. Method 400 may be performed byprocessing logic that may include hardware (e.g., circuitry, dedicatedlogic, programmable logic, microcode, etc.), software (such asinstructions run on a processing device, a general purpose computersystem, or a dedicated machine), firmware, or a combination thereof. Inone embodiment, method 400 may be performed, in part, by the VPGMM unit112 of the processor 102 as shown in FIG. 1.

For simplicity of explanation, the method 400 is depicted and describedas a series of acts. However, acts in accordance with this disclosurecan occur in various orders and/or concurrently and with other acts notpresented and described herein. Furthermore, not all illustrated actsmay be performed to implement the method 400 in accordance with thedisclosed subject matter. In addition, those skilled in the art willunderstand and appreciate that the method 400 could alternatively berepresented as a series of interrelated states via a state diagram orevents.

Method 400 begins at block 402 where an application is enabled to assignpages in its virtual addresses to create a VPG. In one embodiment, a setof pages may be added to the VPG. In one embodiment, a set of pages maybe deleted from the VPG. At block 404, a virtual page group identifier(VPGID) identifying the VPG is assigned to the VPG. At block 406, adefault high caching priority (CP) value is assigned to the VPGID of theVPG. As discussed above, the value assigned to the CP determinesimportance of data in the cache. Also, as discussed above, a value 0 isassigned as the high CP.

FIG. 4B is a flow diagram of method 420 of specifying caching prioritiesof application data. Method 420 may be performed by processing logicthat may include hardware (e.g., circuitry, dedicated logic,programmable logic, microcode, etc.), software (such as instructions runon a processing device, a general purpose computer system, or adedicated machine), firmware, or a combination thereof. In oneembodiment, method 420 may be performed, in part, by the VPGMM unit 112of the processor 102 as shown in FIG. 1.

For simplicity of explanation, the method 420 is depicted and describedas a series of acts. However, acts in accordance with this disclosurecan occur in various orders and/or concurrently and with other acts notpresented and described herein. Furthermore, not all illustrated actsmay be performed to implement the method 420 in accordance with thedisclosed subject matter. In addition, those skilled in the art willunderstand and appreciate that the method 420 could alternatively berepresented as a series of interrelated states via a state diagram orevents.

Method 420 begins at block 422 where a memory request for applicationdata in an application is received by the processing logic. At block424, information associated with the application data of the applicationis determined. In one embodiment, the information includes requirementsof the application. In one embodiment, the information includes type ofapplication data. As discussed above, requirements of the applicationmay include, but are not limited to application's ability to classifyapplication data based on relative importance and ability to convey thisinformation to the system software managing VPGCP table. Also, asdiscussed above, some of the type of the data may include, but is notlimited to, index data and table data in the database.

At block 426, a value assigned to a caching priority (CP) is modifiedfor a corresponding VPGID of the VPG based on the information. Asdiscussed above, a value is assigned to the CP to determine importanceof data in the cache. In one example, CP is a given a numerical value inthe range of 0 to Max_CP where large numbers in the range imply lowercaching priority and higher preference for eviction from the caches andlower numbers in the range imply higher caching priority and lowerpreference for eviction from the caches. Also as discussed above adefault value of 0 indicating the high caching priority (CP) isinitially assigned to the VPG. In one embodiment, the CP value for thecorresponding VPG is modified in the VPGCP table 214. At block 428, themodified CP value applied for the application data in a cache. In oneembodiment, the modified CP value is applied for cache allocation. Inone embodiment, the modified CP value is applied for cache eviction.

FIG. 5A is a block diagram illustrating an in-order pipeline and aregister renaming stage, out-of-order issue/execution pipelineimplemented by processing device 500 according to some embodiments ofthe disclosure. The solid lined boxes in FIG. 5A illustrate an in-orderpipeline, while the dashed lined boxes illustrates a register renaming,out-of-order issue/execution pipeline. In FIG. 5A, a processor pipeline500 includes a fetch stage 502, a length decode stage 504, a decodestage 506, an allocation stage 508, a renaming stage 510, a scheduling(also known as a dispatch or issue) stage 512, a register read/memoryread stage 514, an execute stage 516, a write back/memory write stage518, an exception handling stage 522, and a commit stage 524. In someembodiments, the ordering of stages 502-524 may be different thanillustrated and are not limited to the specific ordering shown in FIG.5A.

FIG. 5B is a block diagram illustrating a micro-architecture for aprocessor 500 that implements the processing device includingheterogeneous cores in accordance with one embodiment of the disclosure.Specifically, processor 500 depicts an in-order architecture core and aregister renaming logic, out-of-order issue/execution logic to beincluded in a processor according to at least one embodiment of thedisclosure.

Processor 500 includes a front end unit 530 coupled to an executionengine unit 550, and both are coupled to a memory unit 570. Theprocessor 500 may include a reduced instruction set computing (RISC)core, a complex instruction set computing (CISC) core, a very longinstruction word (VLIW) core, or a hybrid or alternative core type. Asyet another option, processor 500 may include a special-purpose core,such as, for example, a network or communication core, compressionengine, graphics core, or the like. In one embodiment, processor 500 maybe a multi-core processor or may part of a multi-processor system.

The front end unit 530 includes a branch prediction unit 532 coupled toan instruction cache unit 534, which is coupled to an instructiontranslation lookaside buffer (TLB) 536, which is coupled to aninstruction fetch unit 538, which is coupled to a decode unit 540. Thedecode unit 540 (also known as a decoder) may decode instructions, andgenerate as an output one or more micro-operations, micro-code entrypoints, microinstructions, other instructions, or other control signals,which are decoded from, or which otherwise reflect, or are derived from,the original instructions. The decoder 540 may be implemented usingvarious different mechanisms. Examples of suitable mechanisms include,but are not limited to, look-up tables, hardware implementations,programmable logic arrays (PLAs), microcode read only memories (ROMs),etc. The instruction cache unit 534 is further coupled to the memoryunit 570. The decode unit 540 is coupled to a rename/allocator unit 552in the execution engine unit 550.

The execution engine unit 550 includes the rename/allocator unit 552coupled to a retirement unit 554 and a set of one or more schedulerunit(s) 556. The retirement unit 554 may include a virtual page groupmemory management (VPGMM) unit 503 minimize snoop traffic both locallyand across cores on a chip multi- core fabric according to embodimentsof the invention. The scheduler unit(s) 556 represents any number ofdifferent schedulers, including reservations stations (RS), centralinstruction window, etc. The scheduler unit(s) 556 is coupled to thephysical register file(s) unit(s) 558. Each of the physical registerfile(s) units 558 represents one or more physical register files,different ones of which store one or more different data types, such asscalar integer, scalar floating point, packed integer, packed floatingpoint, vector integer, vector floating point, etc., status (e.g., aninstruction pointer that is the address of the next instruction to beexecuted), etc. The physical register file(s) unit(s) 558 is overlappedby the retirement unit 554 to illustrate various ways in which registerrenaming and out-of-order execution may be implemented (e.g., using areorder buffer(s) and a retirement register file(s), using a futurefile(s), a history buffer(s), and a retirement register file(s); using aregister maps and a pool of registers; etc.).

In one implementation, processor 500 may be the same as processor 102described with respect to FIG. 1.

Generally, the architectural registers are visible from the outside ofthe processor or from a programmer's perspective. The registers are notlimited to any known particular type of circuit. Various different typesof registers are suitable as long as they are capable of storing andproviding data as described herein. Examples of suitable registersinclude, but are not limited to, dedicated physical registers,dynamically allocated physical registers using register renaming,combinations of dedicated and dynamically allocated physical registers,etc. The retirement unit 554 and the physical register file(s) unit(s)558 are coupled to the execution cluster(s) 560. The executioncluster(s) 560 includes a set of one or more execution units 562 and aset of one or more memory access units 564. The execution units 562 mayperform various operations (e.g., shifts, addition, subtraction,multiplication) and operate on various types of data (e.g., scalarfloating point, packed integer, packed floating point, vector integer,vector floating point).

While some embodiments may include a number of execution units dedicatedto specific functions or sets of functions, other embodiments mayinclude only one execution unit or multiple execution units that allperform all functions. The scheduler unit(s) 556, physical registerfile(s) unit(s) 558, and execution cluster(s) 560 are shown as beingpossibly plural because certain embodiments create separate pipelinesfor certain types of data/operations (e.g., a scalar integer pipeline, ascalar floating point/packed integer/packed floating point/vectorinteger/vector floating point pipeline, and/or a memory access pipelinethat each have their own scheduler unit, physical register file(s) unit,and/or execution cluster—and in the case of a separate memory accesspipeline, certain embodiments are implemented in which only theexecution cluster of this pipeline has the memory access unit(s) 564).It should also be understood that where separate pipelines are used, oneor more of these pipelines may be out-of-order issue/execution and therest in-order.

The set of memory access units 564 is coupled to the memory unit 570,which may include a data prefetcher 580, a data TLB unit 572, a datacache unit (DCU) 574, and a level 2 (L2) cache unit 576, to name a fewexamples. In some embodiments DCU 574 is also known as a first leveldata cache (L1 cache). The DCU 574 may handle multiple outstanding cachemisses and continue to service incoming stores and loads. It alsosupports maintaining cache coherency. The data TLB unit 572 is a cacheused to improve virtual address translation speed by mapping virtual andphysical address spaces. In one exemplary embodiment, the memory accessunits 564 may include a load unit, a store address unit, and a storedata unit, each of which is coupled to the data TLB unit 572 in thememory unit 570. The L2 cache unit 576 may be coupled to one or moreother levels of cache and eventually to a main memory.

In one embodiment, the data prefetcher 580 speculativelyloads/prefetches data to the DCU 574 by automatically predicting whichdata a program is about to consume. Prefeteching may refer totransferring data stored in one memory location of a memory hierarchy(e.g., lower level caches or memory) to a higher-level memory locationthat is closer (e.g., yields lower access latency) to the processorbefore the data is actually demanded by the processor. Morespecifically, prefetching may refer to the early retrieval of data fromone of the lower level caches/memory to a data cache and/or prefetchbuffer before the processor issues a demand for the specific data beingreturned.

The processor 500 may support one or more instructions sets (e.g., thex86 instruction set (with some extensions that have been added withnewer versions); the MIPS instruction set of MIPS Technologies ofSunnyvale, Calif.; the ARM instruction set (with optional additionalextensions such as NEON) of ARM Holdings of Sunnyvale, Calif.).

It should be understood that the core may support multithreading(executing two or more parallel sets of operations or threads), and maydo so in a variety of ways including time sliced multithreading,simultaneous multithreading (where a single physical core provides alogical core for each of the threads that physical core issimultaneously multithreading), or a combination thereof (e.g., timesliced fetching and decoding and simultaneous multithreading thereaftersuch as in the Intel® Hyperthreading technology).

While register renaming is described in the context of out-of-orderexecution, it should be understood that register renaming may be used inan in-order architecture. While the illustrated embodiment of theprocessor also includes a separate instruction and data cache units anda shared L2 cache unit, alternative embodiments may have a singleinternal cache for both instructions and data, such as, for example, aLevel 1 (L1) internal cache, or multiple levels of internal cache. Insome embodiments, the system may include a combination of an internalcache and an external cache that is external to the core and/or theprocessor. Alternatively, all of the cache may be external to the coreand/or the processor.

FIG. 6 illustrates a block diagram of the micro-architecture for aprocessor 600 that includes hybrid cores in accordance with oneembodiment of the disclosure. In some embodiments, an instruction inaccordance with one embodiment can be implemented to operate on dataelements having sizes of byte, word, doubleword, quadword, etc., as wellas datatypes, such as single and double precision integer and floatingpoint datatypes. In one embodiment the in-order front end 601 is thepart of the processor 600 that fetches instructions to be executed andprepares them to be used later in the processor pipeline.

The front end 601 may include several units. In one embodiment, theinstruction prefetcher 626 fetches instructions from memory and feedsthem to an instruction decoder 628 which in turn decodes or interpretsthem. For example, in one embodiment, the decoder decodes a receivedinstruction into one or more operations called “micro-instructions” or“micro-operations” (also called micro op or uops) that the machine canexecute. In other embodiments, the decoder parses the instruction intoan opcode and corresponding data and control fields that are used by themicro-architecture to perform operations in accordance with oneembodiment. In one embodiment, the trace cache 630 takes decoded uopsand assembles them into program ordered sequences or traces in the uopqueue 634 for execution. When the trace cache 630 encounters a complexinstruction, the microcode ROM 632 provides the uops needed to completethe operation.

Some instructions are converted into a single micro-op, whereas othersneed several micro-ops to complete the full operation. In oneembodiment, if more than four micro-ops are needed to complete aninstruction, the decoder 628 accesses the microcode ROM 632 to do theinstruction. For one embodiment, an instruction can be decoded into asmall number of micro ops for processing at the instruction decoder 628.In another embodiment, an instruction can be stored within the microcodeROM 632 should a number of micro-ops be needed to accomplish theoperation. The trace cache 630 refers to an entry point programmablelogic array (PLA) to determine a correct micro-instruction pointer forreading the micro-code sequences to complete one or more instructions inaccordance with one embodiment from the micro-code ROM 632. After themicrocode ROM 632 finishes sequencing micro-ops for an instruction, thefront end 601 of the machine resumes fetching micro-ops from the tracecache 630.

The out-of-order execution engine 603 is where the instructions areprepared for execution. The out-of-order execution logic has a number ofbuffers to smooth out and re-order the flow of instructions to optimizeperformance as they go down the pipeline and get scheduled forexecution. The allocator logic allocates the machine buffers andresources that each uop needs in order to execute. The register renaminglogic renames logic registers onto entries in a register file. Theallocator also allocates an entry for each uop in one of the two uopqueues, one for memory operations and one for non-memory operations, infront of the instruction schedulers: memory scheduler, fast scheduler602, slow/general floating point scheduler 604, and simple floatingpoint scheduler 606. The uop schedulers 602, 604, 606, determine when auop is ready to execute based on the readiness of their dependent inputregister operand sources and the availability of the execution resourcesthe uops need to complete their operation. The fast scheduler 602 of oneembodiment can schedule on each half of the main clock cycle while theother schedulers can only schedule once per main processor clock cycle.The schedulers arbitrate for the dispatch ports to schedule uops forexecution.

Register files 608, 610, sit between the schedulers 602, 604, 606, andthe execution units 612, 614, 616, 618, 620, 622, 624 in the executionblock 611. There is a separate register file 608, 610, for integer andfloating point operations, respectively. Each register file 608, 610, ofone embodiment also includes a bypass network that can bypass or forwardjust completed results that have not yet been written into the registerfile to new dependent uops. The integer register file 608 and thefloating point register file 610 are also capable of communicating datawith the other. For one embodiment, the integer register file 608 issplit into two separate register files, one register file for the loworder 32 bits of data and a second register file for the high order 32bits of data. The floating point register file 610 of one embodiment has128 bit wide entries because floating point instructions typically haveoperands from 64 to 128 bits in width.

The execution block 611 contains the execution units 612, 614, 616, 618,620, 622, 624, where the instructions are actually executed. Thissection includes the register files 608, 610, that store the integer andfloating point data operand values that the micro-instructions need toexecute. The processor 600 of one embodiment is comprised of a number ofexecution units: address generation unit (AGU) 612, AGU 614, fast ALU616, fast ALU 618, slow ALU 620, floating point ALU 622, floating pointmove unit 624. For one embodiment, the floating point execution blocks622, 624, execute floating point, MMX, SIMD, and SSE, or otheroperations. The floating point ALU 622 of one embodiment includes a 64bit by 64 bit floating point divider to execute divide, square root, andremainder micro-ops. For embodiments of the present disclosure,instructions involving a floating point value may be handled with thefloating point hardware.

In one embodiment, the ALU operations go to the high-speed ALU executionunits 616, 618. The fast ALUs 616, 618, of one embodiment can executefast operations with an effective latency of half a clock cycle. For oneembodiment, most complex integer operations go to the slow ALU 620 asthe slow ALU 620 includes integer execution hardware for long latencytype of operations, such as a multiplier, shifts, flag logic, and branchprocessing. Memory load/store operations are executed by the AGUs 612,614. For one embodiment, the integer ALUs 616, 618, 620, are describedin the context of performing integer operations on 64 bit data operands.In alternative embodiments, the ALUs 616, 618, 620, can be implementedto support a variety of data bits including 16, 32, 128, 256, etc.Similarly, the floating point units 622, 624, can be implemented tosupport a range of operands having bits of various widths. For oneembodiment, the floating point units 622, 624, can operate on 128 bitswide packed data operands in conjunction with SIMD and multimediainstructions.

In one embodiment, the uops schedulers 602, 604, 606, dispatch dependentoperations before the parent load has finished executing. As uops arespeculatively scheduled and executed in processor 600, the processor 600also includes logic to handle memory misses. If a data load misses inthe data cache, there can be dependent operations in flight in thepipeline that have left the scheduler with temporarily incorrect data. Areplay mechanism tracks and re-executes instructions that use incorrectdata. Only the dependent operations need to be replayed and theindependent ones are allowed to complete. The schedulers and replaymechanism of one embodiment of a processor are also designed to catchinstruction sequences for text string comparison operations.

The processor 600 also includes logic to implement store addressprediction for memory disambiguation according to embodiments of thedisclosure. In one embodiment, the execution block 611 of processor 600may include a store address predictor (not shown) for implementing storeaddress prediction for memory disambiguation.

The processor 600 may include a retirement unit 654 coupled to theexecution block 611. The retirement unit 654 may include a virtual pagegroup memory management (VPGMM) unit 605 to minimize snoop traffic bothlocally and across cores on a chip multi-core fabric according toembodiments of the invention.

The term “registers” may refer to the on-board processor storagelocations that are used as part of instructions to identify operands. Inother words, registers may be those that are usable from the outside ofthe processor (from a programmer's perspective). However, the registersof an embodiment should not be limited in meaning to a particular typeof circuit. Rather, a register of an embodiment is capable of storingand providing data, and performing the functions described herein. Theregisters described herein can be implemented by circuitry within aprocessor using any number of different techniques, such as dedicatedphysical registers, dynamically allocated physical registers usingregister renaming, combinations of dedicated and dynamically allocatedphysical registers, etc. In one embodiment, integer registers storethirty-two bit integer data. A register file of one embodiment alsocontains eight multimedia SIMD registers for packed data.

For the discussions below, the registers are understood to be dataregisters designed to hold packed data, such as 64 bits wide MMXTMregisters (also referred to as ‘mm’ registers in some instances) inmicroprocessors enabled with MMX technology from Intel Corporation ofSanta Clara, Calif. These MMX registers, available in both integer andfloating point forms, can operate with packed data elements thataccompany SIMD and SSE instructions. Similarly, 128 bits wide XMMregisters relating to SSE2, SSE3, SSE4, or beyond (referred togenerically as “SSEx”) technology can also be used to hold such packeddata operands. In one embodiment, in storing packed data and integerdata, the registers do not need to differentiate between the two datatypes. In one embodiment, integer and floating point are eithercontained in the same register file or different register files.Furthermore, in one embodiment, floating point and integer data may bestored in different registers or the same registers.

Referring now to FIG. 7, shown is a block diagram illustrating a system700 in which an embodiment of the disclosure may be used. As shown inFIG. 7, multiprocessor system 700 is a point-to-point interconnectsystem, and includes a first processor 770 and a second processor 780coupled via a point-to-point interconnect 750. While shown with only twoprocessors 770, 780, it is to be understood that the scope ofembodiments of the disclosure is not so limited. In other embodiments,one or more additional processors may be present in a given processor.In one embodiment, the multiprocessor system 700 may implement hybridcores as described herein.

Processors 770 and 780 are shown including integrated memory controllerunits 772 and 782, respectively. Processor 770 also includes as part ofits bus controller units point-to-point (P-P) interfaces 776 and 778;similarly, second processor 780 includes P-P interfaces 786 and 788.Processors 770, 780 may exchange information via a point-to-point (P-P)interface 750 using P-P interface circuits 778, 788. As shown in FIG. 7,IMCs 772 and 782 couple the processors to respective memories, namely amemory 732 and a memory 734, which may be portions of main memorylocally attached to the respective processors.

Processors 770, 780 may each exchange information with a chipset 790 viaindividual P-P interfaces 752, 754 using point to point interfacecircuits 776, 794, 786, 798. Chipset 790 may also exchange informationwith a high-performance graphics circuit 738 via a high-performancegraphics interface 739.

A shared cache (not shown) may be included in either processor oroutside of both processors, yet connected with the processors via P-Pinterconnect, such that either or both processors' local cacheinformation may be stored in the shared cache if a processor is placedinto a low power mode.

Chipset 790 may be coupled to a first bus 716 via an interface 796. Inone embodiment, first bus 716 may be a Peripheral Component Interconnect(PCI) bus, or a bus such as a PCI Express bus or another thirdgeneration I/O interconnect bus, although the scope of the presentdisclosure is not so limited.

As shown in FIG. 7, various I/O devices 714 may be coupled to first bus716, along with a bus bridge 718 which couples first bus 716 to a secondbus 720. In one embodiment, second bus 720 may be a low pin count (LPC)bus. Various devices may be coupled to second bus 720 including, forexample, a keyboard and/or mouse 722, communication devices 727 and astorage unit 728 such as a disk drive or other mass storage device whichmay include instructions/code and data 730, in one embodiment. Further,an audio I/O 724 may be coupled to second bus 720. Note that otherarchitectures are possible. For example, instead of the point-to-pointarchitecture of FIG. 7, a system may implement a multi-drop bus or othersuch architecture.

Referring now to FIG. 8, shown is a block diagram of a system 800 inwhich one embodiment of the disclosure may operate. The system 800 mayinclude one or more processors 810, 815, which are coupled to graphicsmemory controller hub (GMCH) 820. The optional nature of additionalprocessors 815 is denoted in FIG. 8 with broken lines. In oneembodiment, processors 810, 815 implement hybrid cores according toembodiments of the disclosure.

Each processor 810, 815 may be some version of the circuit, integratedcircuit, processor, and/or silicon integrated circuit as describedabove. However, it should be noted that it is unlikely that integratedgraphics logic and integrated memory control units would exist in theprocessors 810, 815. FIG. 8 illustrates that the GMCH 820 may be coupledto a memory 840 that may be, for example, a dynamic random access memory(DRAM). The DRAM may, for at least one embodiment, be associated with anon-volatile cache.

The GMCH 820 may be a chipset, or a portion of a chipset. The GMCH 820may communicate with the processor(s) 810, 815 and control interactionbetween the processor(s) 810, 815 and memory 840. The GMCH 820 may alsoact as an accelerated bus interface between the processor(s) 810, 815and other elements of the system 800. For at least one embodiment, theGMCH 820 communicates with the processor(s) 810, 815 via a multi-dropbus, such as a frontside bus (FSB) 895.

Furthermore, GMCH 820 is coupled to a display 845 (such as a flat panelor touchscreen display). GMCH 820 may include an integrated graphicsaccelerator. GMCH 820 is further coupled to an input/output (I/O)controller hub (ICH) 850, which may be used to couple various peripheraldevices to system 800. Shown for example in the embodiment of FIG. 8 isan external graphics device 860, which may be a discrete graphicsdevice, coupled to ICH 850, along with another peripheral device 870.

Alternatively, additional or different processors may also be present inthe system 800. For example, additional processor(s) 815 may includeadditional processors(s) that are the same as processor 810, additionalprocessor(s) that are heterogeneous or asymmetric to processor 810,accelerators (such as, e.g., graphics accelerators or digital signalprocessing (DSP) units), field programmable gate arrays, or any otherprocessor. There can be a variety of differences between theprocessor(s) 810, 815 in terms of a spectrum of metrics of meritincluding architectural, micro-architectural, thermal, power consumptioncharacteristics, and the like. These differences may effectivelymanifest themselves as asymmetry and heterogeneity amongst theprocessors 810, 815. For at least one embodiment, the various processors810, 815 may reside in the same die package.

Referring now to FIG. 9, shown is a block diagram of a system 900 inwhich an embodiment of the disclosure may operate. FIG. 9 illustratesprocessors 970, 980. In one embodiment, processors 970, 980 mayimplement hybrid cores as described above. Processors 970, 980 mayinclude integrated memory and I/O control logic (“CL”) 972 and 982,respectively and intercommunicate with each other via point-to-pointinterconnect 950 between point-to-point (P-P) interfaces 978 and 988respectively. Processors 970, 980 each communicate with chipset 990 viapoint-to-point interconnects 952 and 954 through the respective P-Pinterfaces 976 to 994 and 986 to 998 as shown. For at least oneembodiment, the CL 972, 982 may include integrated memory controllerunits. CLs 972, 982 may include I/O control logic. As depicted, memories932, 934 coupled to CLs 972, 982 and I/O devices 914 are also coupled tothe control logic 972, 982. Legacy I/O devices 915 are coupled to thechipset 990 via interface 996.

Embodiments may be implemented in many different system types. FIG. 10is a block diagram of a SoC 1000 in accordance with an embodiment of thepresent disclosure. Dashed lined boxes are optional features on moreadvanced SoCs. In FIG. 10, an interconnect unit(s) 1012 is coupled to:an application processor 1020 which includes a set of one or more cores1002A-N and shared cache unit(s) 1006; a system agent unit 1010; a buscontroller unit(s) 1016; an integrated memory controller unit(s) 1014; aset or one or more media processors 1018 which may include integratedgraphics logic 1008, an image processor 1024 for providing still and/orvideo camera functionality, an audio processor 1026 for providinghardware audio acceleration, and a video processor 1028 for providingvideo encode/decode acceleration; an static random access memory (SRAM)unit 1030; a direct memory access (DMA) unit 1032; and a display unit1040 for coupling to one or more external displays. In one embodiment, amemory module may be included in the integrated memory controllerunit(s) 1014. In another embodiment, the memory module may be includedin one or more other components of the SoC 1000 that may be used toaccess and/or control a memory. The application processor 1020 mayinclude a store address predictor for implementing hybrid cores asdescribed in embodiments herein.

The memory hierarchy includes one or more levels of cache within thecores, a set or one or more shared cache units 1006, and external memory(not shown) coupled to the set of integrated memory controller units1014. The set of shared cache units 1006 may include one or moremid-level caches, such as level 2 (L2), level 3 (L3), level 4 (L4), orother levels of cache, a last level cache (LLC), and/or combinationsthereof.

In some embodiments, one or more of the cores 1002A-N are capable ofmulti-threading. The system agent 1010 includes those componentscoordinating and operating cores 1002A-N. The system agent unit 1010 mayinclude for example a power control unit (PCU) and a display unit. ThePCU may be or include logic and components needed for regulating thepower state of the cores 1002A-N and the integrated graphics logic 1008.The display unit is for driving one or more externally connecteddisplays.

The cores 1002A-N may be homogenous or heterogeneous in terms ofarchitecture and/or instruction set. For example, some of the cores1002A-N may be in order while others are out-of-order. As anotherexample, two or more of the cores 1002A-N may be capable of executionthe same instruction set, while others may be capable of executing onlya subset of that instruction set or a different instruction set.

The application processor 1020 may be a general-purpose processor, suchas a Core™ i3, i5, i7, 2 Duo and Quad, Xeon™, Itanium™, Atom™ or Quark™processor, which are available from Intel™ Corporation, of Santa Clara,Calif. Alternatively, the application processor 1020 may be from anothercompany, such as ARM Holdings™, Ltd, MIPS™, etc. The applicationprocessor 1020 may be a special-purpose processor, such as, for example,a network or communication processor, compression engine, graphicsprocessor, co-processor, embedded processor, or the like. Theapplication processor 1020 may be implemented on one or more chips. Theapplication processor 1020 may be a part of and/or may be implemented onone or more substrates using any of a number of process technologies,such as, for example, BiCMOS, CMOS, or NMOS.

FIG. 11 is a block diagram of an embodiment of a system on-chip (SoC)design in accordance with the present disclosure. As a specificillustrative example, SoC 1100 is included in user equipment (UE). Inone embodiment, UE refers to any device to be used by an end-user tocommunicate, such as a hand-held phone, smartphone, tablet, ultra-thinnotebook, notebook with broadband adapter, or any other similarcommunication device. Often a UE connects to a base station or node,which potentially corresponds in nature to a mobile station (MS) in aGSM network.

Here, SOC 1100 includes 2 cores—1106 and 1107. Cores 1106 and 1107 mayconform to an Instruction Set Architecture, such as an Intel®Architecture Core™-based processor, an Advanced Micro Devices, Inc.(AMD) processor, a MIPS-based processor, an ARM-based processor design,or a customer thereof, as well as their licensees or adopters. Cores1106 and 1107 are coupled to cache control 1108 that is associated withbus interface unit 1109 and L2 cache 1110 to communicate with otherparts of system 1100. Interconnect 1110 includes an on-chipinterconnect, such as an IOSF, AMBA, or other interconnect discussedabove, which potentially implements one or more aspects of the describeddisclosure. In one embodiment, cores 1106, 1107 may implement hybridcores as described in embodiments herein.

Interconnect 1110 provides communication channels to the othercomponents, such as a Subscriber Identity Module (SIM) 1130 to interfacewith a SIM card, a boot ROM 1135 to hold boot code for execution bycores 1106 and 1107 to initialize and boot SoC 1100, a SDRAM controller1140 to interface with external memory (e.g. DRAM 1160), a flashcontroller 1145 to interface with non-volatile memory (e.g. Flash 1165),a peripheral control 1150 (e.g. Serial Peripheral Interface) tointerface with peripherals, video codecs 1120 and Video interface 1125to display and receive input (e.g. touch enabled input), GPU 1115 toperform graphics related computations, etc. Any of these interfaces mayincorporate aspects of the disclosure described herein. In addition, thesystem 1100 illustrates peripherals for communication, such as aBluetooth module 1170, 3G modem 1175, GPS 1180, and Wi-Fi 1185.

FIG. 12 illustrates a diagrammatic representation of a machine in theexample form of a computer system 1200 within which a set ofinstructions, for causing the machine to perform any one or more of themethodologies discussed herein, may be executed. In alternativeembodiments, the machine may be connected (e.g., networked) to othermachines in a LAN, an intranet, an extranet, or the Internet. Themachine may operate in the capacity of a server or a client device in aclient-server network environment, or as a peer machine in apeer-to-peer (or distributed) network environment. The machine may be apersonal computer (PC), a tablet PC, a set-top box (STB), a PersonalDigital Assistant (PDA), a cellular telephone, a web appliance, aserver, a network router, switch or bridge, or any machine capable ofexecuting a set of instructions (sequential or otherwise) that specifyactions to be taken by that machine. Further, while only a singlemachine is illustrated, the term “machine” shall also be taken toinclude any collection of machines that individually or jointly executea set (or multiple sets) of instructions to perform any one or more ofthe methodologies discussed herein.

The computer system 1200 includes a processing device 1202, a mainmemory 1204 (e.g., read-only memory (ROM), flash memory, dynamic randomaccess memory (DRAM) (such as synchronous DRAM (SDRAM) or DRAM (RDRAM),etc.), a static memory 1206 (e.g., flash memory, static random accessmemory (SRAM), etc.), and a data storage device 1218, which communicatewith each other via a bus 1230.

Processing device 1202 represents one or more general-purpose processingdevices such as a microprocessor, central processing unit, or the like.More particularly, the processing device may be complex instruction setcomputing (CISC) microprocessor, reduced instruction set computer (RISC)microprocessor, very long instruction word (VLIW) microprocessor, orprocessor implementing other instruction sets, or processorsimplementing a combination of instruction sets. Processing device 1202may also be one or more special-purpose processing devices such as anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA), a digital signal processor (DSP), network processor,or the like. In one embodiment, processing device 1202 may include oneor processing cores. The processing device 1202 is configured to executethe processing logic 1226 for performing the operations and stepsdiscussed herein. In one embodiment, processing device 1202 is the sameas processor architecture 100 described with respect to FIG. 1 asdescribed herein with embodiments of the disclosure.

The computer system 1200 may further include a network interface device1208 communicably coupled to a network 1220. The computer system 1200also may include a video display unit 1210 (e.g., a liquid crystaldisplay (LCD) or a cathode ray tube (CRT)), an alphanumeric input device1212 (e.g., a keyboard), a cursor control device 1214 (e.g., a mouse),and a signal generation device 1216 (e.g., a speaker). Furthermore,computer system 1200 may include a graphics processing unit 1222, avideo processing unit 1228, and an audio processing unit 1232.

The data storage device 1218 may include a machine-accessible storagemedium 1224 on which is stored software 1226 implementing any one ormore of the methodologies of functions described herein, such asimplementing store address prediction for memory disambiguation asdescribed above. The software 1226 may also reside, completely or atleast partially, within the main memory 1204 as instructions 1226 and/orwithin the processing device 1202 as processing logic 1226 duringexecution thereof by the computer system 1200; the main memory 1204 andthe processing device 1202 also constituting machine-accessible storagemedia.

The machine-readable storage medium 1224 may also be used to storeinstructions 1226 implementing store address prediction for hybrid coressuch as described according to embodiments of the disclosure. While themachine-accessible storage medium 1128 is shown in an example embodimentto be a single medium, the term “machine-accessible storage medium”should be taken to include a single medium or multiple media (e.g., acentralized or distributed database, and/or associated caches andservers) that store the one or more sets of instructions. The term“machine-accessible storage medium” shall also be taken to include anymedium that is capable of storing, encoding or carrying a set ofinstruction for execution by the machine and that cause the machine toperform any one or more of the methodologies of the present disclosure.The term “machine-accessible storage medium” shall accordingly be takento include, but not be limited to, solid-state memories, and optical andmagnetic media.

The following examples pertain to further embodiments.

Example 1 is a processor comprising a processing core to generate amemory request for application data in an application and a virtual pagegroup memory management (VPGMM) unit, coupled to the processing core tospecify a caching priority (CP) to the application data for theapplication.

In Example 2, the subject matter of Example 1 can optionally includewherein the VPGMM unit to assign pages in a virtual address of theapplication to create a virtual page group (VPG).

In Example 3, the subject matter of any one of Examples 1-2 canoptionally include wherein the VPGMM unit to assign a default value tothe CP associated with the VPG.

In Example 4, the subject matter of any one of Examples 1-3 canoptionally include wherein the VPGMM unit to modify the default value ofthe CP associated with the VPG.

In Example 5, the subject matter of any one of Examples 1-4 canoptionally include wherein the VPGMM unit to modify the default value ofthe CP associated with the VPG in view of type of the application data.

In Example 6, the subject matter of any one of Examples 1-5 canoptionally include wherein the VPGMM unit to modify the default value ofthe CP associated with the VPG in view of at least one requirement ofthe application.

In Example 7, the subject matter of any one of Examples 1-6 canoptionally include wherein the modified default value of the CP isapplied for the memory request for the application data in the cache.

Example 8 is a system-on-a chip (SoC) comprising a memory and aprocessor, communicatively coupled to the memory, comprising aprocessing core to generate a memory request for an application data inan application; and a virtual page group memory management (VPGMM) unit,coupled to the processing core to specify a caching priority (CP) to theapplication data for the application.

In Example 9, the subject matter of Example 8 can optionally includewherein the VPGMM unit to assign pages in a virtual address of theapplication to create a virtual page group (VPG).

In Example 10, the subject matter of any one of Examples 8-9 canoptionally include wherein the VPGMM unit to modify a value of the CPassociated with the VPG.

Example 11 is a method comprising receiving a memory request for anapplication data in an application; and specifying a caching priority(CP) to the application data for the application, wherein the cachingpriority identifies importance of the application data in a cache.

In Example 12, the subject matter of Example 11 can optionally includeassigning pages in a virtual address of the application to create avirtual page group (VPG).

In Example 13, the subject matter of any one of Examples 11-12 canoptionally include assigning a default value to the CP associated withthe VPG.

In Example 14, the subject matter of any one of Examples 11-13 canoptionally include modifying the default value of the CP associated withthe VPG in view of type of the application data.

In Example 15, the subject matter of any one of Examples 11-14 canoptionally include modifying the default value of the CP associated withthe VPG in view of at least one requirement of the application.

Example 16 is a non-transitory machine-readable storage medium includingdata that, when accessed by a processing device, cause the processingdevice to perform operations comprising receiving a memory request foran application data in an application; and specifying a caching priority(CP) to the application data for the application.

In Example 17, the subject matter of Example 16 can optionally includewherein the operations further comprising assigning pages in a virtualaddress of the application to create a virtual page group (VPG).

In Example 18, the subject matter of any one of Examples 16-17 canoptionally include wherein the operations further comprising assigning adefault value to the CP associated with the VPG.

In Example 19, the subject matter of any one of Examples 16-18 canoptionally include wherein the operations further comprising modifyingthe default value of the CP associated with the VPG in view of type ofthe application data.

In Example 20, the subject matter of any one of Examples 16-19 canoptionally include wherein the operations further comprising modifyingthe default value of the CP associated with the VPG in view of at leastone requirement of the application.

While the disclosure has been described with respect to a limited numberof embodiments, those skilled in the art will appreciate numerousmodifications and variations there from. It is intended that theappended claims cover all such modifications and variations as fallwithin the true spirit and scope of this disclosure.

A design may go through various stages, from creation to simulation tofabrication. Data representing a design may represent the design in anumber of manners. First, as is useful in simulations, the hardware maybe represented using a hardware description language or anotherfunctional description language. Additionally, a circuit level modelwith logic and/or transistor gates may be produced at some stages of thedesign process. Furthermore, most designs, at some stage, reach a levelof data representing the physical placement of various devices in thehardware model. In the case where conventional semiconductor fabricationtechniques are used, the data representing the hardware model may be thedata specifying the presence or absence of various features on differentmask layers for masks used to produce the integrated circuit. In anyrepresentation of the design, the data may be stored in any form of amachine readable medium. A memory or a magnetic or optical storage suchas a disc may be the machine readable medium to store informationtransmitted via optical or electrical wave modulated or otherwisegenerated to transmit such information. When an electrical carrier waveindicating or carrying the code or design is transmitted, to the extentthat copying, buffering, or re-transmission of the electrical signal isperformed, a new copy is made. Thus, a communication provider or anetwork provider may store on a tangible, machine-readable medium, atleast temporarily, an article, such as information encoded into acarrier wave, embodying techniques of embodiments of the presentdisclosure.

A module as used herein refers to any combination of hardware, software,and/or firmware. As an example, a module includes hardware, such as amicro-controller, associated with a non-transitory medium to store codeadapted to be executed by the micro-controller. Therefore, reference toa module, in one embodiment, refers to the hardware, which isspecifically configured to recognize and/or execute the code to be heldon a non-transitory medium. Furthermore, in another embodiment, use of amodule refers to the non-transitory medium including the code, which isspecifically adapted to be executed by the microcontroller to performpredetermined operations. And as can be inferred, in yet anotherembodiment, the term module (in this example) may refer to thecombination of the microcontroller and the non-transitory medium. Oftenmodule boundaries that are illustrated as separate commonly vary andpotentially overlap. For example, a first and a second module may sharehardware, software, firmware, or a combination thereof, whilepotentially retaining some independent hardware, software, or firmware.In one embodiment, use of the term logic includes hardware, such astransistors, registers, or other hardware, such as programmable logicdevices.

Use of the phrase ‘configured to,’ in one embodiment, refers toarranging, putting together, manufacturing, offering to sell, importingand/or designing an apparatus, hardware, logic, or element to perform adesignated or determined task. In this example, an apparatus or elementthereof that is not operating is still ‘configured to’ perform adesignated task if it is designed, coupled, and/or interconnected toperform said designated task. As a purely illustrative example, a logicgate may provide a 0 or a 1 during operation. But a logic gate‘configured to’ provide an enable signal to a clock does not includeevery potential logic gate that may provide a 1 or 0. Instead, the logicgate is one coupled in some manner that during operation the 1 or 0output is to enable the clock. Note once again that use of the term‘configured to’ does not require operation, but instead focus on thelatent state of an apparatus, hardware, and/or element, where in thelatent state the apparatus, hardware, and/or element is designed toperform a particular task when the apparatus, hardware, and/or elementis operating.

Furthermore, use of the phrases ‘to,’ capable of/to,' and or ‘operableto,’ in one embodiment, refers to some apparatus, logic, hardware,and/or element designed in such a way to enable use of the apparatus,logic, hardware, and/or element in a specified manner. Note as abovethat use of to, capable to, or operable to, in one embodiment, refers tothe latent state of an apparatus, logic, hardware, and/or element, wherethe apparatus, logic, hardware, and/or element is not operating but isdesigned in such a manner to enable use of an apparatus in a specifiedmanner.

A value, as used herein, includes any known representation of a number,a state, a logical state, or a binary logical state. Often, the use oflogic levels, logic values, or logical values is also referred to as 1'sand 0's, which simply represents binary logic states. For example, a 1refers to a high logic level and 0 refers to a low logic level. In oneembodiment, a storage cell, such as a transistor or flash cell, may becapable of holding a single logical value or multiple logical values.However, other representations of values in computer systems have beenused. For example the decimal number ten may also be represented as abinary value of 910 and a hexadecimal letter A. Therefore, a valueincludes any representation of information capable of being held in acomputer system.

Moreover, states may be represented by values or portions of values. Asan example, a first value, such as a logical one, may represent adefault or initial state, while a second value, such as a logical zero,may represent a non-default state. In addition, the terms reset and set,in one embodiment, refer to a default and an updated value or state,respectively. For example, a default value potentially includes a highlogical value, i.e. reset, while an updated value potentially includes alow logical value, i.e. set. Note that any combination of values may beutilized to represent any number of states.

The embodiments of methods, hardware, software, firmware or code setforth above may be implemented via instructions or code stored on amachine-accessible, machine readable, computer accessible, or computerreadable medium which are executable by a processing element. Anon-transitory machine-accessible/readable medium includes any mechanismthat provides (i.e., stores and/or transmits) information in a formreadable by a machine, such as a computer or electronic system. Forexample, a non-transitory machine-accessible medium includesrandom-access memory (RAM), such as static RAM (SRAM) or dynamic RAM(DRAM); ROM; magnetic or optical storage medium; flash memory devices;electrical storage devices; optical storage devices; acoustical storagedevices; other form of storage devices for holding information receivedfrom transitory (propagated) signals (e.g., carrier waves, infraredsignals, digital signals); etc., which are to be distinguished from thenon-transitory mediums that may receive information there from.

Instructions used to program logic to perform embodiments of thedisclosure may be stored within a memory in the system, such as DRAM,cache, flash memory, or other storage. Furthermore, the instructions canbe distributed via a network or by way of other computer readable media.Thus a machine-readable medium may include any mechanism for storing ortransmitting information in a form readable by a machine (e.g., acomputer), but is not limited to, floppy diskettes, optical disks,Compact Disc, Read-Only Memory (CD-ROMs), and magneto-optical disks,Read-Only Memory (ROMs), Random Access Memory (RAM), ErasableProgrammable Read-Only Memory (EPROM), Electrically ErasableProgrammable Read-Only Memory (EEPROM), magnetic or optical cards, flashmemory, or a tangible, machine-readable storage used in the transmissionof information over the Internet via electrical, optical, acoustical orother forms of propagated signals (e.g., carrier waves, infraredsignals, digital signals, etc.). Accordingly, the computer-readablemedium includes any type of tangible machine-readable medium suitablefor storing or transmitting electronic instructions or information in aform readable by a machine (e.g., a computer).

Reference throughout this specification to “one embodiment” or “anembodiment” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment of the present disclosure. Thus, theappearances of the phrases “in one embodiment” or “in an embodiment” invarious places throughout this specification are not necessarily allreferring to the same embodiment. Furthermore, the particular features,structures, or characteristics may be combined in any suitable manner inone or more embodiments.

In the foregoing specification, a detailed description has been givenwith reference to specific exemplary embodiments. It will, however, beevident that various modifications and changes may be made theretowithout departing from the broader spirit and scope of the disclosure asset forth in the appended claims. The specification and drawings are,accordingly, to be regarded in an illustrative sense rather than arestrictive sense. Furthermore, the foregoing use of embodiment andother exemplarily language does not necessarily refer to the sameembodiment or the same example, but may refer to different and distinctembodiments, as well as potentially the same embodiment.

1. A processor comprising: a processing core to generate a memoryrequest for application data in an application; and a virtual page groupmemory management (VPGMM) unit, coupled to the processing core,comprising a caching priority (CP) table indexed by virtual page groupidentifications (VPGIDs), wherein a CP value in an entry of the CP tableindexed by a VPGID corresponding to the application data indicates a CPof the application data for the application.
 2. The processor of claim1, wherein the VPGMM unit to assign pages in a virtual address of theapplication to create a virtual page group (VPG).
 3. The processor ofclaim 2, wherein the VPGMM unit to assign a default value to the CPassociated with the VPG.
 4. The processor of claim 3 wherein the VPGMMunit to modify the default value of the CP associated with the VPG. 5.The processor of claim 4, wherein the VPGMM unit to modify the defaultvalue of the CP associated with the VPG in view of type of theapplication data.
 6. The processor of claim 4, wherein the VPGMM unit tomodify the default value of the CP associated with the VPG in view of atleast one requirement of the application.
 7. The processor of claim 4,wherein the modified default value of the CP is applied for the memoryrequest for the application data in the cache.
 8. A system-on-a chip(SoC) comprising: a memory; and a processor, communicably coupled to thememory, comprising: a processing core to generate a memory request foran application data in an application; and a virtual page group memorymanagement (VPGMM) unit, coupled to the processing core, comprising acaching priority (CP) table indexed by virtual page groupidentifications (VPGIDs), wherein a CP value in an entry of the CP tableindexed by a VPGID corresponding to the application data indicates a CPof the application data for the application.
 9. The SoC of claim 8,wherein the VPGMM unit to assign pages in a virtual address of theapplication to create a virtual page group (VPG).
 10. The SoC of claim 9wherein the VPGMM unit to modify a value of the CP associated with theVPG.
 11. A method comprising: receiving a memory request for anapplication data in an application; identifying a caching priority (CP)value in an entry of a CP table of a virtual page group memorymanagement (VPGMM) unit, the CP table indexed by virtual page groupidentifications (VPGIDs), wherein the identified CP value is indexed bya VPGID corresponding to the application data; and specifying a cachingpriority corresponding to the identified CP value to the applicationdata for the application, wherein the caching priority identifiesimportance of the application data in a cache.
 12. The method of claim11 further comprising assigning pages in a virtual address of theapplication to create a virtual page group (VPG).
 13. The method ofclaim 12 further comprising assigning a default value to the CPassociated with the VPG.
 14. The method of claim 13 further comprisingmodifying the default value of the CP associated with the VPG in view oftype of the application data.
 15. The method of claim 13 furthercomprising modifying the default value of the CP associated with the VPGin view of at least one requirement of the application.
 16. Anon-transitory machine-readable storage medium including instructionsthat, when accessed by a processing device, cause the processing deviceto perform operations comprising: receiving a memory request for anapplication data in an application; identifying a caching priority (CP)value in an entry of a CP table of a virtual page group memorymanagement (VPGMM) unit, the CP table indexed by virtual page groupidentifications (VPGIDs), wherein the identified CP value is indexed bya VPGID corresponding to the application data; and specifying a cachingpriority corresponding to the identified CP value to the applicationdata for the application.
 17. The non-transitory machine-readablestorage medium of claim 16, wherein the operations further comprisingassigning pages in a virtual address of the application to create avirtual page group (VPG).
 18. The non-transitory machine-readablestorage medium of claim 17, wherein the operations further comprisingassigning a default value to the CP associated with the VPG.
 19. Thenon-transitory machine-readable storage medium of claim 18, wherein theoperations further comprising modifying the default value of the CPassociated with the VPG in view of type of the application data.
 20. Thenon-transitory machine-readable storage medium of claim 18, wherein theoperations further comprising modifying the default value of the CPassociated with the VPG in view of at least one requirement of theapplication.